-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement LibuvStream interface for BufferStream #35545
Conversation
It is noted as a non-OS stream, but has also been a subtype of LibuvStream since forever. #32309 did not add the `readerror` field.
No; if |
Hi! Looking forward to seeing this in 1.4 branch, as this PR is crucial to run my parallel Julia code with MPI.jl on a cluster. |
It looks like UDPSocket is the remaining subtype of LibuvStream that doesn't have this. Not sure if it's needed. |
If possible at all, I'd be so glad to see this in v1.4.2 (also for MPI.jl). |
Seems like too substantial a change for a bugfix release. Could happen in 1.5 though. |
What is too substantial? The struct layout change? |
I misinterpreted this PR as changing the type hierarchy, not just changing the doc to reflect reality there. Just adding a field may be fine in a point release. @JeffBezanson's call I think. |
I think the bugfix value of this outweighs any possible problems. |
It is noted as a non-OS stream, but has also been a subtype
of LibuvStream since forever. #32309 did not add the
readerror
field.
It might be better to decouple
BufferStream
from theLibuvStream
interface, but I decided to be conservative. Are changes in the type-hierarchy
backportable?